Skip to content

Conversation

@Dark-Athena
Copy link

@Dark-Athena Dark-Athena commented Jul 26, 2025

Introduces baud rate selection for serial port connections in the UI and persists the value in local storage. Adds a settings reset tab to the menu, allowing users to clear all application settings and reload. Updates i18n files for new UI strings and refactors serial port logic to support dynamic baud rate changes.

image image image

Introduces baud rate selection for serial port connections in the UI and persists the value in local storage. Adds a settings reset tab to the menu, allowing users to clear all application settings and reload. Updates i18n files for new UI strings and refactors serial port logic to support dynamic baud rate changes.
@wj-xiao
Copy link
Collaborator

wj-xiao commented Oct 30, 2025

Apologies for the delay in our response.
Thanks a lot for your contribution and the effort you put into this!

We've done some extensive testing with different baud rates, and our findings show that the default 57600 provides the most stable and smooth user experience. Other baud rates, unfortunately, can lead to lagging or even connection failures.

For this reason, we are cautious about introducing a feature that allows users to change the baud rate, as it might degrade their experience unless they are certain about what they are doing. We need to carefully consider whether this functionality should be added.

We are very open to hearing more of your thoughts on this. Do you have any suggestions on how we could implement this safely?

Thanks again for your excellent work!

@wj-xiao wj-xiao mentioned this pull request Oct 30, 2025
@Dark-Athena
Copy link
Author

Apologies for the delay in our response. Thanks a lot for your contribution and the effort you put into this!

We've done some extensive testing with different baud rates, and our findings show that the default 57600 provides the most stable and smooth user experience. Other baud rates, unfortunately, can lead to lagging or even connection failures.

For this reason, we are cautious about introducing a feature that allows users to change the baud rate, as it might degrade their experience unless they are certain about what they are doing. We need to carefully consider whether this functionality should be added.

We are very open to hearing more of your thoughts on this. Do you have any suggestions on how we could implement this safely?

Thanks again for your excellent work!

The NanoKVM-USB has the cleanest and most refreshing user interface among the several software options with similar functions that I've used, and its operation is quite smooth.
However, I'd like the NanoKVM-USB to support third-party hardware, such as a DIY setup using MS2130 + CH9329 + CH340. Although the CH9329 supports various baud rates, the baud rate of purchased CH9329 chips might be random. While it's possible to modify the CH9329's baud rate through certain methods, there remains a technical barrier (during urgent situations, there's no time for on-site maintenance personnel to learn how to change the baud rate). Therefore, to simplify the use of such DIY solutions, a relatively convenient and universal method would be to add support for specifying the baud rate on the NanoKVM-USB itself. If the selected baud rate is incompatible with the hardware, the connection will fail, requiring users to know exactly what baud rate their serial device uses. If an incorrect baud rate is selected by mistake, a reset settings function could initialize the configuration, preventing the system from automatically using the wrong baud rate for the next connection.
Since I have set 57600 as the default baud rate, this change should not significantly impact the user experience for those using the official NanoKVM-USB hardware.

Below is a screenshot of software that can modify the baud rate of a serial device.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants